home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
1,000 Game Levels 2
/
1,000 Game Levels 2.iso
/
DOSRPG
/
BTRIP10.ZIP
/
BATTLE.DOC
next >
Wrap
Text File
|
1994-10-22
|
21KB
|
506 lines
_____________________________________________________________________
Battle Trip v1.0
Written by
Rob Williams
WCS Software
_____________________________________________________________________
Table of Contents
-----------------
Copyright Notice................................................... 1
Warranty........................................................... 1
Features of Battle Trip............................................ 2
Files used in the program.......................................... 3
Setting up Battle Trip............................................. 4
Setting up Battle Trip for Multinode Play.......................... 5
Playing the game................................................... 6
Make-Up Days Explanation........................................... 7
Special Keys....................................................... 8
Support............................................................ 9
Registering Battle Trip............................................ 9
Acknowledgements................................................... 10
Copyright Notice
----------------
This door game is distributed under the SHAREWARE concept. This
concept gives you the chance to "try before you buy", and see if it
meets your needs.
I've decided to break away from the standard "30 day trial period"
that many door authors are using and instead go to a much simpler
and more realistic policy. This is simply; Try it on your BBS.
If you like it and your users like it, then register it. If it's not
good enough to register, then delete it.
While I'd like you to register my doors as soon as possible, I'm also
realistic enough to know that different boards have different requirements
and interests, and sometimes it takes longer befor a game catches on, or a
sysop can get to the Doors on his list to register. And frankly, I'd
rather you ran it for awhile and register, than try it for a short
period of time and delete it. Nobody wins that way...I lose out on a
registration and your users lose out on the chance of having the
registered door to play.
The above "extended trial" statement was copied with permission from
Mike Jordan of M&S Doors.
As a shareware program, Battle Trip may be freely distributed.
Shareware distributors may distribute copies of Battle Trip on disk
for a modest disk duplication charge not to exceed $4 per disk.
Warranty
--------
Battle Trip is distributed on as as is basis. In no event will
Rob Williams or WCS Software be liable to you for damages, including
any loss of profits, lost savings, or other incidental or
consequential damages arising out of your use of or inability to use
this program, even if Rob Williams, WCS Software, or an authorized
representative has been advised of the possibility of such damages.
Rob Williams and WCS Software will not be liable for any such claim
by any other party.
Features of Battle Trip
-----------------------
Assembly language serial input/output routines for maximum speed.
Fully supports high speed modems: 16550 FIFO buffering and locked
serial ports.
Built in ANSI terminal emulator. No need to have ANSI.SYS loaded in
memory.
DesqView, Windows, and OS/2 aware.
Supports all of the most popular door data file formats:
TriBBS, PCBoard, GAP (DOOR.SYS), Spitfire, WildCat!, RBBS, and WWIV.
ANSI and ASCII Bulletins of high scorers.
Automatic monthly maintenance with no intervention from the Sysop.
Supports play ahead and make up days when registered. This is
completely sysop configurable.
Battle Trip is Multinode Aware!
Files used in the Program
-------------------------
BATTLE.EXE - The main battle trip program
REGISTER.FRM - Information on registration
SAMPLE.CFG - Sample configuration file
SAMPLE.BAT - Sample batch file to run battle trip
HISCORE.DAT - Created when the program runs-contains hi score info
USER.DAT - Created when the program runs-contains user info
BATTLE.KEY - Key file for registered versions
BATTLE.USE - Created when the game is running, will be deleted
when the user exits normally.
(only in single user/non-registered versions)
************************************************************************
** IMPORTANT - The game will not run if this file (BATTLE.USE) exists **
************************************************************************
BATTLE.HLP - Help file for the game. When the Instructions option
is selected, this file is displayed. You may edit
this file if you wish. It is a plain ASCII text file.
BATTLE.HIS - History of the product. Shows what enhancements were
made in what version.
WCSINFO.TXT - A text file explaining more about WCS Software and
showing all currently available WCS Software programs.
READ.ME - A brief text file explaining how to get up and running
quickly.
Setting up Battle Trip
----------------------
Battle Trip is run by entering a command similar to the
following:
BATTLE BATTLE.CFG
The configuration file can have any name you choose, but it must
reside in the same directory as the door. The configuration file is
an ASCII text file with the following format:
Line 1: Door data file type.
Line 2: Path to the door data file(s).
Line 3: BBS name.
Line 4: Sysop's name.
Line 5: Locked baud rate.
Line 6: ASCII High Score Bulletin Name
Line 7: ANSI High Score Bulletin Name
Line 8: Number of Games per day
* Line 9: Number of extra days allowed for make up days
* Line 10: Day to start playing make up days-31 to disable
Line 11: Write log file (YES or NO)
* Line 12: Line to display a message (donated by, etc)
Line 13: Name you want the computer opponent to have
Lines with a "*" to the left indicate features only present in the
registered version of the program. *** The lines must be present,
even if the door is not registered. ***
As illustrated above, the door's data file type is specified in line 1
and can be PCB for PCBoard, GAP for GAP (DOOR.SYS), SF for Spitfire,
RBBS for RBBS, WC for WildCat!, TRIBBS for TriBBS, or WWIV for WWIV.
The locked baud rate is specified in line 5. If you don't lock your
serial port, you must specify 0 for the locked baud rate.
The following is a sample door configuration file:
************************************************************************
** IMPORTANT - If you are running WC 4.x, use the GAP drop file **
************************************************************************
WC <== BBS Type
C:\WC30\WCWORK\NODE1 <== Drop file location
WCS Software BBS <== BBS Name
Rob Williams <== Sysop Name
0 <== Locked baud rate
C:\WC30\BULL\BULL10.BBS <== ASCII bulletin
C:\WC30\BULL\BULL10.SCR <== ANSI bulletin
10 <== # of questions per day
2 <== Extra days allowed for make up days
10 <== Day to start make up days
YES <== Write a log file (BATTLE.nodenumber)
By WCS Software <== Donated by line
Computers Name <== Name as you want it to appear for
computer opponent
************************************************************************
** IMPORTANT - Even if the game is not registered, the last three **
** lines must exist, or the game will not run. You will get an error **
** when the game starts up. **
************************************************************************
Battle Trip can be run locally without a door data file (handy
for the sysop to use the door without logging on to the BBS) by
specifying /L after the configuration file parameter in the DOS
command line. BT will request you to enter your name before running
the door.
To play the game in Multiuser mode, you must have a registered multinode
copy,and DOS SHARE must be loaded. If these two things are not done,
the game will display a message if you try to run multinode.
Nonstandard IRQs can be used by specifying the IRQ number after the
"config" parameter in the command line used to run the door as
follows:
BATTLE BATTLE.CFG 4
Setting up Battle Trip for Multinode Play
-----------------------------------------
In order to set Battle Trip up for multinode play, you need to create a
.cfg file for each node that will be using the game. The .cfg files
will be similar, except that lines 2 and possibly 5 will be different.
Line 2 is the location of the door drop file. This needs to be unique
for each node that runs the game. Line 5 is the locked baud rate for
the node. If you have nodes that are locked at different rates, then
this line may be different for different nodes. For example, the
configuration file for node 1 (BATTLE.CF1) might look like this:
GAP
H:\WILDCAT\WCWORK\NODE1 <=== Notice this is the node 1 directory
Williams Computer Services BBS
Rob Williams
19200
[etc].....
And the configuration file for node 2 (BATTLE.CF2) might look like this:
GAP
H:\WILDCAT\WCWORK\NODE2 <=== Notice this is the node 2 directory
Williams Computer Services BBS
Rob Williams
19200
[etc].....
You will also need to set an environment variable to tell the program
what node it is currently running on. Since I run Wildcat, I call
this variable WCNODEID. In my .BAT file that calls the BBS, I set the
WCNODEID to whatever node is running. You can use wahtever name you
wish, it just needs to be a unique node ID.
Next, in the batch file that calls BT, you would change the sample.bat
that is included with this archive to look like this:
CD\BATTLE
BATTLE BATTLE.CF%WCNODEID%
What this will do, is when the game is started, it will look for the
WCNODEID (or whatever you called it), and append that to BATTLE.CF. So
when the game runs, and you run it from node 1 say, it will use .cfg file
BATTLE.CF1.
Hopefully, I have not totally confused you on how to set the door up for
mult-node use. If you have questions on environment variables, refer
to your DOS manual.
**************************************************************************
** Running this game on more than a single node requires a Multi-Node **
** Key. When running in Evaluation mode, only one (1) Node will be able**
** to access the door at a time. **
**************************************************************************
Playing the Game
----------------
Battle Trip is based on the card game Mille Borne. When you enter the
door, you come to a menu of four options. They are:
P)lay Battle Trip - Starts the game
H)igh scores - Shows the high score bulletin
I)nstructions - Displays this file
Q)uit - Exits the game
Available Keys
--------------
After choosing the "P" option from the main menu, you are brought to the
main play screen. From this screen there are four options:
P)lay card - To play a card from your hand
D)iscard - To discard a card from your hand
C)oup Fourre - To play a safety on a hazard on your battle pile
R)edraw Screen - Redraws the screen if you get line noise, etc.
H)igh scores - Shows the high score bulletin
I)nstructions - Displays this file
Q)uit - Exits the game
Parts of the Game
-----------------
There are four different types of cards in the game.
Hazards - Out of gas, Flat Tire, Accident, Speed Limit, Stop
Remedies - Gasoline, Spare Tire, Repairs, End of Limit, Roll
Safeties - Extra Tank, Puncture Proof, Driving Ace, Right of Way
Distance - 200, 100 75, 50, 25 miles
The board is laid out as follows:
Battle Pile : This is where you play hazards (except for speed limits)
on the computers pile, and remedies on your pile. To
play a distance card, you must have a roll card on top
of your battle pile.
Speed Pile : This is where you play speed limits (on the computers
pile), and end of limits (on your pile)
Safety : This is where you play any safety cards you have. Once
you play a safety card, the computer cannot play the
associated hazard card.
Distance Pile-You cannot see these stacks, but you do see the total
distance you have travelled under Total Miles.
The object of the game is to "travel" 1000 miles before the computer does.
To play miles, you must have a Roll card on the top of your battle pile.
If you have a speed limit on your speed pile, you cannot travel any
further than 50 miles in a trip.
During each turn, you will draw a card from the pile, and then either
P)lay, D)iscard, or C)oup Fourre a card. To start, you need to play a
Roll card, then you can play distance cards as long as you have a roll
card on top of your battle pile.
If you have played all your games for the day, you will be asked if you
want to view the high scores. Then you will be returned to the BBS.
Scoring
-------
For each game, you are scored as follows:
Miles Played : As shown
Safeties Played : 100 for each safety played
Coup Fourees : 300 for each safety that was coup foureed
Trip Completed : 400 points for completing the trip
Safe Trip : 300 points if no 200 mile cards were played
All safeties : 300 points if you play all 4 safeties
Shut Out : 500 points if you complete trip and computer has 0 miles
When you go into the door, you will see an opening screen, it will
wait for you to press a key, then show you the main menu. From here,
there are four options. P will take you to the playing screen, H will
show you the high score list, I will show you a help file for playing
the game, and Q will return you to the BBS.
The first time a player plays the game each month, the system will
automatically reset the player statistics. This process should not
take more than a few seconds, and is automatic, so no intervention
from the Sysop is necessary.
Make-Up Days Explanation
------------------------
The make up days feature warrants a little more explanation here.
When the game is registered, after you have played your game for today,
it will check to see if make up days has been enabled (start day < 31).
If today is greater than the start day, and the total number of days you
have played is not greater than what was specified in the .cfg file, it
will ask you if you want to play a make up day. It will then show a
calendar of days for the current month. Days that you have played will
show up in red with an x, playable days will show up in green with an o.
Choose a valid date (one with an o, within the current month), and you
will start another days game. If you changed your mind and do not want
to play a make up day, enter 99, and you will be asked if you want to
view the high scores, then be returned to the BBS.
Special Keys
------------
While BT is running, the sysop can press certain special keys to
perform a variety of functions. The following is a list of the
functions that the special keys perform:
Key(s) Function
HOME Toggles between the user status window and a help
display that lists the special keys.
F6 Takes 5 minutes away from the caller.
NOTE: This will NOT be returned to BBS.
F7 Gives 5 minutes to the caller.
NOTE: This will NOT be returned to the BBS.
F9 Quit the door and return the caller to the BBS.
F10 Enter chat mode. Pressing the ESC key exits the
chat mode.
Alt+D Drop to DOS.
Support
-------
If you have problems, I will try and help as best I can, whether you
are registered or not. Registered users will get priority over non-
registered users, though. You may get help with problems by calling
Williams Computer Services BBS at (503) 631-8439, or by writing to
the author at the following addresses:
FIDO : 1:105/278
Internet via FIDO gateway : rob.williams@f278.n105.z1.fidonet.org
US Mail:
Rob Williams
18370 S. Henrici Road
Oregon City, OR 97045
Registering Battle Trip
-----------------------------
Registration of Battle Trip is only $15.00 for single node
or $20.00 for Multi-Node. Please use the form in the file
REGISTER.FRM. When you register, you will receive a registration
key that will turn your version into a registered version.
Registered users will have access to the special area of the support
BBS for additional questions, and also be able to add new questions,
edit questions and users, print questions and users, and import and
export questions.
***** ALL UPDATES ARE FREE FOR THE LIFE OF THE PROGRAM *****
Acknowledgements
----------------
Thanks go to the following people/companies (Listed in no particular order):
- Mustang Software for creating Wildcat!
- Randy Hunt and Mark Goodwin for creating RMDoor which was used
to create this game.
- Mike Jordan for his help with some of the routines, and for the
idea of the make up days, and also help in testing, and his help
in helping me get started in door programming.
- Andy Stewart for his programming help, and also for creating the
main play screen.
- Marcus and Ronda Eikenberry for their help in testing and finding
a few stubborn bugs.
- Gayle Davis and all the people that have contributed to the
SWAG archives. I have used various snippets from those
archives, as well as them giving me good ideas on how to
proceed next. Thank you.
There are probably more people that I have forgotten, but these have been
the most instrumental in the writing of this program.